Systems and methods for providing card interactions

ABSTRACT

A method including receiving a first application user credential associated with a user profile; comparing, for a first match, the first application user credential with a stored second application user credential, wherein the stored second application user credential is associated with a user identity; and responsive to finding a first match, verifying the user identity by performing the following: communicating with a card using near field communication; receiving a public key of a key pair of the card and cardholder identification information of an account holder of the card; instructing the card to generate a digital signature; receiving the digital signature from the card; verifying the digital signature using the public key; and comparing, for a second match, at least a portion of the user identity with at least a portion of the cardholder identification information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of, and claims priority under 35 U.S.C.§ 121 to, U.S. patent application Ser. No. 16/135,954, filed Sep. 19,2018, the entire contents and substance of which is hereby incorporatedby reference in their entirety.

FIELD

The presently disclosed subject matter relates generally to systemsmethods for providing interactions between a contactless device and auser device, and, more particularly, to systems and methods forauthenticating a user and/or providing other account functions to acardholder based on an authenticated communication between a contactlesstransaction card and a user device of the cardholder.

BACKGROUND

Activating many cards, and more specifically financial cards (e.g.,credit cards), involve the time-consuming process of cardholders callinga telephone number or visiting a website and entering or otherwiseproviding card information. Further, while the growing use of chip-basedfinancial cards provides more secure features over the previoustechnology (e.g., magnetic strip cards) for in-person purchases, accountaccess still typically relies on log-in credentials (e.g., username andpassword) to confirm a cardholder's identity. However, if the log-incredentials are compromised, another person could have access to theuser's account.

Accordingly, there is a need for both an improved method of activating acard and an improved authentication for account access.

SUMMARY

Aspects of the disclosed technology include systems and methods forproviding authenticated cardholder access. Consistent with the disclosedembodiments, the systems and methods may utilize one or more computingdevices, processors, web servers, account servers, and/or contactlessdevices (e.g., radio frequency identification (RFID) cards). A methodmay include an application executing on a computing device receiving afirst application user credential associated with a user profile. Aprocessor associated with the application compares the first applicationuser credential with a stored second application user credential. Thestored second application user credential is associated with a useridentity (e.g., a user account or user profile). In response to findinga match, the user may be authenticated to access the application. Insome embodiments, the user identity may be further verified (e.g.,second or multi-factor authentication) via an authenticationcommunication protocol between the computing device and a contactlessdevice.

For example, in some embodiments, the authentication communicationprotocol may be established as part of a wireless communication betweena transaction card (e.g., a credit card associated with the user)through the use of near field communication (NFC) with the computingdevice (e.g., a smartphone). The authentication communication protocolmay include receiving a digital signature from the transaction card,verifying the digital signature, and comparing at least a portion ofcard information to user account information (e.g., comparing the useridentity with at least a portion of cardholder identificationinformation). In some embodiments, the authentication communicationprotocol may conform to an offline dynamic data authentication protocolor an offline combined data authentication protocol as part of an EMVstandard. In some embodiments, the authentication communication protocolbetween the contactless device and a user computing device may includeone or more steps that mimic an authentication protocol between acontactless transaction card and a point-of-sale device, except in thedisclosed embodiments, the authentication protocol is not used tocomplete a payment transaction and does not require real-time onlineconnectivity to an issuer of the transaction card. Furthermore, theexample authentication communication protocol disclosed herein may beused as a form of authentication for a user associated with thecomputing device (as opposed to a point of sale device) as detailedherein. And because the example authentication communication protocoluses two NFC capabilities (e.g., READ and WRITE), the example techniquesuse dynamic data and public and private keys to validate the signaturesand certificates of the card issuer, the card, the user, and theinteraction between the transaction card and a user's computing device,as detailed below. The example embodiments are thus advantageous overother NFC techniques that use only READ capability to perform staticdata check methods, such as to obtain a primary account number (PAN) ofa transaction card, and thus lack the security available via offlinedynamic data authentication. Thus, the example embodiments uniquely takeadvantage of the strong security of offline dynamic data authenticationtechniques to establish an authentication communication protocol betweena transaction card and a user's computing device to achieve a trustedform of authentication that may be used to activate a card, as a form ofmultifactor authentication, and/or to unlock other functionality of amobile application.

A contactless device (e.g., card, tag, transaction card or the like) mayuse near field communications technology for bi-directional oruni-directional contactless short-range communications based on, forexample, radio frequency identification (RFID) standards, an EMVstandard, or using NFC Data Exchange Format (NDEF) tags. Thecommunication may use magnetic field induction to enable communicationbetween electronic devices, including mobile wireless communicationsdevices. Short-range high frequency wireless communications technologyenables the exchange of data between devices over a short distance, suchas only a few centimeters.

In the present disclosure, authentication or verification of acontactless device based on the completion of an example authenticationcommunication protocol between a contactless device and a user computingdevice may be a primary form of authentication or a secondary form ofauthentication. Furthermore, completion of an example authenticationcommunication protocol between the contactless device and a usercomputing device may enable other functionality. For example, in someembodiments, a cardholder can activate a contactless card based on theexample authentication communication protocol by tapping it against auser computing device (e.g., a mobile device) implementing a cardreader. For example, the device may include a card reader antenna (e.g.,an NFC antenna) which may send and receive information with acontactless card, and an application executing on the device may beconfigured to implement card reading capabilities with the card reader.Through NFC, a communication link is established between the contactlesscard and the application. After establishing the communication link, thecard transmits cardholder data including a digital signature to theapplication. Based on the digital signature (e.g. upon authentication ofthe card), the application recogizes the card as belonging to a specificaccount server (e.g., associated with a specific customer account). Theapplication communicates data associated with the card to the specificaccount server and requests activation of the card. The account serveractivates the card within its system and transmits an indicaton of thesuccess of the activation to the application. The application thendisplays the status of the card activation to the user.

The contactless card may also be linked to user credentials to providegreater account access. A user may enter user credentials to log ontothe application. The application verifies the user credentials bycomparing, for at least a portion of a match, the user credentials tostored user credentials. Once verified, the user may access certainfirst-level user account options. For greater access and/or executingcertain account functions, i.e., second-level user account options,second-factor authentication may be required. For example, thecontactless card may be tapped against the user device whilecard-reading is enabled. The application may communicate with the card(e.g., through NFC). The application may receive cardholder data and/ora digital signature from the card, and the application compares thecardholder data to a user identity associated with the user. If thecardholder data corresponds to the user identity, the user may accesssecond-level user account options.

In an example scenario, to log a user into an application, anapplication associated with a computing device (e.g., smartphone)receives a user's credentials. The user credentials could be, forexample, biometrics data (e.g., fingerprint data, optical data, and/orfacial recognition), an established gesture associated with the user,and/or a username and password combination. A processor associated withthe application performs a check of the provided application usercredentials against a stored application user credential. The firstmatch allows the user access to first-level user account options (e.g.,display of account balance, display of recent transactions). A secondlevel of authentication may be required to access second-level useraccount options. The second level of authentication may involve theapplication communicating with a transaction card by using a card readerassociated with the computing device. From the transaction card, theapplication receives cardholder identification information of an accountholder of the transaction card. Using a certificate authority publickey, the application extracts an issuer public key from the transactioncard. The application uses the issuer public key to extract the cardpublic key of a key pair. The application then instructs the transactioncard to generate a digital signature by using a private key of the keypair of the transaction card. Using the card public key, the applicationverifies the digital signature. To perform second-factor authentication,the processor compares, for a second match, at least a portion of theuser identity with at least a portion of the cardholder identificationinformation. For example, the processor may compare the user's name fromthe user identity with the user's name associated with the cardholderidentification information. Upon authentication, the application grantsthe user access to several second-level user account options including apayment transfer, a payment request, a personal identification number(PIN) change request, and an address change request.

Further features of the disclosed design, and the advantages offeredthereby, are explained in greater detail hereinafter with reference tospecific example embodiments illustrated in the accompanying drawings,wherein like elements are indicated be like reference designators.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and which are incorporated into andconstitute a portion of this disclosure, illustrate variousimplementations and aspects of the disclosed technology and, togetherwith the description, serve to explain the principles of the disclosedtechnology. In the drawings:

FIG. 1 is a diagram of an example environment that may be used toimplement one or more embodiments of the present disclosure.

FIG. 2 is a timing diagram providing authenticated cardholder accessaccording to an example embodiment.

FIG. 3 is a timing diagram of peer-to-peer transfer according to anexample embodiment.

FIG. 4 is a flow chart of a method providing authenticated cardholderaccess according to an example embodiment.

FIG. 5 is a flow chart of a method providing authenticated cardholderaccess according to an example embodiment.

FIG. 6 is a flow chart of a method providing activation of a cardaccording to an example embodiment.

FIG. 7 is a flow chart of a method for pairing a card to a deviceaccording to an example embodiment.

FIG. 8 is a block diagram of an example computer system that mayimplement certain aspects of the present disclosure.

FIG. 9 is a flow chart of a method for activating a contactless cardaccording to an example embodiment.

FIG. 10 is a timing diagram of authenticated cardholder access accordingto an example embodiment.

DETAILED DESCRIPTION

Some implementations of the disclosed technology will be described morefully with reference to the accompanying drawings. The disclosedtechnology may, however, be embodied in many different forms and shouldnot be construed as limited to the implementations set forth herein. Thecomponents described hereinafter as making up various elements of thedisclosed technology are intended to be illustrative and notrestrictive. Many suitable components that would perform the same orsimilar functions as components described herein are intended to beembraced within the scope of the disclosed electronic devices andmethods. Such other components not described herein may include, but arenot limited to, for example, components developed after development ofthe disclosed technology.

It is also to be understood that the mention of one or more method stepsdoes not preclude the presence of additional method steps or interveningmethod steps between those steps expressly identified.

Reference will now be made in detail to exemplary embodiments of thedisclosed technology, examples of which are illustrated in theaccompanying drawings and disclosed herein. Wherever convenient, thesame references numbers will be used throughout the drawings to refer tothe same or like parts.

FIG. 1 shows an example environment 100 that may implement certainaspects of the present disclosure. The components and arrangements shownin FIG. 1 are not intended to limit the disclosed embodiments as thecomponents used to implement the disclosed processes and features mayvary. As shown in FIG. 1, in some implementations the environment 100includes one or more contactless cards 110 a and 110 b, one or morecomputing devices 120 which include one or more applications 122 and oneor more processors 124, a network 130, a web server 140 which mayinclude a processor 142 and a database 144, and an account server 150(e.g., a server of a card issuer or card manager). As non-limitingexamples, the computing device 120 may be a personal computer, asmartphone, a laptop computer, a tablet, or other personal computingdevice. The network 130 may include a network of interconnectedcomputing devices more commonly referred to as the internet. The webserver 140 may include one or more physical or logical devices (e.g.,servers). The computing device 120 may run and display one or moreapplications and the related output(s) of the one or more applications(e.g, through APIs) 122. The computing device 120 may include a cardreader 126 or one or more components that may function to read fromand/or communicate with a contactless card (e.g., a digital cardreader). In conjunction with the one or more applications 122, the cardreader 126 communicates with the one or more contactless cards 110 a and110 b (e.g., RFID cards). An example computer architecture that may beused to implement one or more of the computing device 120, the accountserver 150 and the web server 140 is described below with reference toFIG. 8.

In certain implementations according to the present disclosure, thecontactless card 110 a and/or 110 b includes a radio frequencyidentification chip enabled to communicate via near field communication(NFC) or other short-range communication protocols. In otherembodiments, the contactless card 110 a may communicate through othermeans including, but not limited to, Bluetooth, satellite, and/or WiFi.According to some embodiments, the contactless card 110 a communicateswith the card reader 126 through near field communication when thecontactless card 110 a is within range of the card reader 126. Thecontactless card 110 a may send to the application 122 a certificateauthority public key and cardholder identification information of anaccount holder. The cardholder identification information may include apersonal identification number (PIN), a name of the user, an address, adate of birth, and/or the like. In response to instructions from theapplication 122, the contactless card 110 a may extract the issuerpublic key from the contactless card 110 a. The application 122 uses theissuer public key to extract the card public key of a key pair from thecontactless card 110 a. The application 122 may instruct the contactlesscard 110 a to generate a digital signature using the card private key ofthe key pair. In some embodiments, the contactless card 110 a may sendthe digital signature to the computing device 120.

Turning to the computing device 120, in some embodiments, the computingdevice 120 includes an application 122 and a processor 124. According tosome embodiments, the application 122 receives, from a user, a firstapplication user credential associated with a user profile. The firstapplication user credential may include biometrics data, an establishedgesture associated with user recognition, a username and passwordcombination, and/or the like. The processor 124 compares the firstapplication user credential with a stored second application usercredential. The stored second application user credential may beassociated with the user identity. In some embodiments, the storedsecond application user credential is maintained on a web server 140 andthe first match is performed by the web server 140. In some embodiments,upon determining a first match between the first application usercredential and the stored second application user credential, theapplication 122 may grant the user access to one or more first-leveluser account options of a user account. The user account may be afinancial account, a health insurance account, and/or any other accountof the like associated with any service provider (e.g., a transitaccount, an entertainment account, etc.). The first-level user accountoptions of a user account may include a display of an account balance, adisplay of recent transactions, and/or the like.

After determining the first match, in response to one or more actionsassociated with the application or an account, the computing device 120may further verify the user identity by communicating with thecontactless card 110 a, and verifying the contactless card 110 acorresponds to the user account. The application 122 may communicatewith the contactless card 110 a using short-range wireless communication(e.g., near field communication (NFC)). The application 122 may beconfigured to interface with a card reader 126 of computing device 120capable of communicating with a contactless card. As should be noted,those skilled in the art would understand that a distance of less thantwenty centimeters is consistent with NFC range.

In some embodiments, the application 122 communicates through anassociated reader (e.g., card reader 126) with the contactless card 110a. The application 122 may receive, from the contactless card 110 a, apublic key of a key pair of the card and cardholder identificationinformation of an account holder of the card. The cardholderidentification information may include a personal identification number(PIN), a name of the user, an address, a date of birth, and/or the like.In response to instructions from the application 122, the contactlesscard 110 a may extract the issuer public key from the contactless card110 a. The application 122 uses the issuer public key to extract thecard public key of a key pair from the contactless card 110 a. Theapplication 122 may instruct the contactless card 110 a to generate adigital signature using a private key of the key pair of the contactlesscard 110 a. The computing device 120 verifies the digital signatureusing the card public key. The processor 124 compares at least a portionof the user identity with at least a portion of the cardholderidentification information. In some embodiments, upon determining asecond match between the user identity (e.g., the identity previouslyauthenticated by application 122) and the cardholder identificationinformation obtained from the contactless card, the application 122grants the user access to one or more second-level user account optionsof a user account. According to some embodiments, the second-level useraccount options have a higher security requirement than the first-leveluser account options. As non-limiting examples, the second-level useraccount options of a user account may include a payment transfer, apayment request, a personal identification number (PIN) change request,an address change request, a card activation, and/or the like.

In some embodiments, card activation may occur without first-level userauthentication. For example, a contactless card 110 a may communicatewith the application 122 through the card reader 126 of the computingdevice through NFC. The communication (e.g., a tap of the card proximatethe card reader 126 of the computing device 120) allows the application122 to read the data associated with the card and perform an activation.In some cases, the tap may activate or launch application 122 and theninitiate one or more actions or communications with an account server(e.g., 150) to activate the card for subsequent use. In some cases, ifthe application 122 is not installed on computing device 120, a tap ofthe card against the card reader 126 may initiate a download of theapplication 122 (e.g., navigation to an application download page).Subsequent to installation, a tap of the card may activate or launch theapplication 122, and then initiate (e.g., via the application or otherback-end communication) activation of the card. After activation, thecard may be used in various transactions including commercialtransactions.

According to some embodiments, the contactless card 110 a is a virtualpayment card. In those embodiments, the application 122 may retrieveinformation associated with the contactless card 110 a by accessing adigital wallet implemented on the computing device 120, wherein thedigital wallet includes the virtual payment card.

FIG. 2 is a timing diagram illustrating an example sequence forproviding authenticated cardholder access according to an exampleembodiment. According to some embodiments, at 202 the application 122receives the first application user credentials. A user may provide thefirst application user credentials after receiving a prompt from theapplication 122. The first application user credentials may includebiometrics data, an established gesture associated with userrecognition, a username and password combination, facial recognition,and/or the like. At 204, the application 122 communicates the firstapplication user credentials to the processor 124. The processor 124compares the first application user credentials with stored secondapplication user credential, at 206. The stored second application usercredential may be located within a database associated with thecomputing device 120 or with application 120. In some embodiments, thestored second application user credential is maintained on a server(e.g., account server 150), the first application user credential isprovided to the server, and the server compares the first applicationuser credential to the stored second application user credential.

At 208, the processor 124 communicates the comparison result to theapplication 122 (e.g., for a match). In some embodiments, a first matchgrants the user access to first-level user account options of a useraccount (e.g., display of an account balance and/or recenttransactions). Responsive to finding a first match, at 210, theapplication 122 initiates verifying the user identity. For example, theapplication 122 may output for display on the computing device 120 anotification to bring a contactless card 110 a near the computing device120. At 212, the application 122 communicates with the contactless card110 a (e.g., after being brought near the contactless card 110 a).Communication between the application 122 and the contactless card 110 amay involve the contactless card 110 a being sufficiently close to thecard reader 126 of the computing device to enable NFC data transferbetween the application 122 and the contactless card 110 a. At 214, thecontactless card 110 a sends, to the application 122, a public key of apublic/private key pair and cardholder identification information of anaccount holder of the card. The application 122, at 216, instructs thecontactless card 110 a to generate a digital signature using a privatekey of the key pair of the card. In some cases, the cardholderidentification information may be incorporated within the digitalsignature or otherwise conveyed with the digital signature.

At 218, the contactless card 110 a sends the digital signature to theapplication 122. At 220, the application 122 communicates the digitalsignature with the processor 124. The processor 124, at 222, verifiesthe digital signature using the public key. For example, the card mayprovide a hash of the card's public key encrypted by a trusted source(e.g., a private key of a card provider), and verifying the digitalsignature may include: decrypting the encrypted hash (e.g., with apublic key of the card provider); calculating a new hash of the digitalsignature; and comparing the decrypted original hash to the new hash fora match, at which point the card provider (e.g., issuer), and thetransaction card may be authenticated. By using this READ and WRITE NFCcapability to perform offline dynamic data authentication between acontactless card and a user's computing device, the example embodimentsprovide unique advantages that enable application 122 to more reliably(e.g., with greater security from counterfeiting or card skimming, orman in the middle attacks) authenticate a contactless card to be used asa form of multifactor authentication. As disclosed below in FIG. 10,communication between the application 122 and the contactless card 110 amay include additional interactions. At 224, the processor 124 comparesat least a portion of the user identity with at least a portion of thecardholder identification information. In some embodiments, a secondmatch grants the user access to second-level user account options of auser account (e.g., a payment request, a payment transfer, a cardactivation, a personal identification number (PIN) change request, andan address change request). According to some embodiments, thesecond-level user account options represent more secured features of theapplication 122.

In some cases, verifying the digital signature may be performed by aserver connected to the computing device. For example, processor 124 mayoutput the digital signature for transmission to account server 150, andaccount server 150 may verify the digital signature.

FIG. 3 is a timing diagram of peer-to-peer transfer according to anexample embodiment. In some embodiments, the application 122 may prompta user for first application user credentials. At 302, the application122 receives the first application user credentials. The firstapplication user credentials may include biometrics data, an establishedgesture associated with user recognition, a username and passwordcombination, facial recognition, and/or the like. The application 122communicates the first application user credentials to the processor124, at 304. At 306, the processor 124 transmits the first applicationuser credentials to the web server 140. The web server 140, at 308,compares the first application user credentials to a second storedapplication user credential stored located on the web server 140 (e.g.,to see if they match). At 310, the web server 140 transmits the matchresult to the processor 124. The processor 124, at 312, communicates thematch result to the application 122. At 314, in response to a matchbeing found, the application 122 provides access to the user account.

At 316, the application 122 receives an indication requesting apeer-to-peer transfer (e.g., an indication of a payor or a payee fromthe user account). For example, the user may select a request paymentoption. The peer-to-peer transfer may require authentication, such asrequesting cardholder identification data for comparison to the useridentity. At 318, the application 122 communicates with the contactlesscard 110 a. Communication between the application 122 and thecontactless card 110 a may involve the contactless card 110 a beingsufficiently close to the card reader 126 of the computing device toenable NFC between the application 122 and the contactless card 110 a.The contactless card 110 a sends the public key of a public/private keypair and cardholder identification information to the application 122 at320. At 322, the application 122 instructs the contactless card 110 a togenerate a digital signature using a private key of the key pair of thecard. In some cases, the digital signature may include the cardholderidentification information.

At 324, the contactless card 110 a sends the digital signature to theapplication 122. At 326, the application 122 communicates the digitalsignature to the processor 124. The processor 124 verifies the digitalsignature at 328. At 330, the processor 124 compares (e.g., for amatch), at least a portion of the user identity with at least a portionof the cardholder identification information. If the digital signatureand cardholder identification are verified, at 331 the application 122may request communication with a second transaction card from a seconduser.

In some embodiments the method may further include, at 332, processingthe second transaction card (e.g., the other one of payor or payee) fromthe second user. At 332, the application processes the payment from thesecond user and requested by the first user. Processing the payment mayinvolve communicating with the second contactless card 110 b at 334. Asmentioned above, communication between the application 122 and thesecond contactless card 110 b may include the application 122 havingaccess to card reader 126 (e.g., a digital reader) of the computingdevice 120, and the second contactless card 110 b having an RFID chip.The contactless card 110 b may be sufficiently close to the card reader126 to enable near field communication therebetween. At 336, the secondcontactless card 110 b sends data associated with the card to theapplication 122. The application 122 communicates the data associatedwith the second contactless card 110 b to the processor 124 at 338. At340, the processor 124 transmits the data associated with the secondcontactless card 110 b and a payment authorization request to theaccount server 150. The account server 150 processes the payment requestby either approving or denying the payment.

At 342, the account server 150 sends a status indicator of the paymentrequest to the processor 124. The status indicator of the paymentrequest may include an approved status indicator or a declined statusindicator. At 344, the processor 124 communicates the status indicatorof the payment request to the application 122. At 346, the application122 displays a visual representation of the status indicator on thecomputing device 120.

FIG. 4 is a flow chart of a method providing authenticated cardholderaccess according to an example embodiment. At 402, the application 122receives, from a user, a first application user credential associatedwith a user profile. As mentioned above, a user may provide the firstapplication user credentials after receiving a prompt from theapplication 122. In some embodiments, the first application usercredential may include biometrics data, an established gestureassociated with user recognition, a username and password combination,and/or the like. At 404, the processor 124 compares the firstapplication user credential with a stored second application usercredential. The stored second application user credential may beassociated with a user identity. The user identity may include apersonal identification number (PIN), a name of the user, an address, adate of birth, and/or the like.

According to some embodiments, after finding a first match, theapplication 122 grants access to first-level user account optionsincluding a display of an account, a display of recent transactions,and/or the like. In response to finding a match, the computing device120 verifies the user identity. At 406, the application 122 communicateswith the contactless card 110 a, for example, via an RFID chip in thecontactless card 110 a. The application 122 is associated with a cardreader 126 allowing near field communication between the contactlesscard 110 a and the application 122. At 408, the application 122 receivesa public key of a public/private key pair of the card from thecontactless card 110 a. At 408, the application may also receive cardinformation of the contactless card 110 a. The card information mayinclude cardholder information such as a personal identification number(PIN), a name of the user, an address, a date of birth, and/or the like.At 410, the application 122 instructs the contactless card 110 a togenerate a digital signature by using a private key of the key pair ofthe card. The contactless card 110 a generates the digital signature,and the application 122 receives the digital signature from thecontactless card 110 a at 412. At 414, the computing device 120 verifiesthe digital signature by using the public key of the key pair of thecard.

At 416, the processor 124 compares the card information to the useraccount. For example, processor 124 may compare the user identity tocardholder identification information. In some embodiments afterverifying using the contactless card 110 a, the application 122 grantsaccess to second-level user account options including, as non-limitingexamples, a payment request, a payment transfer, a card activation, apersonal identification number (PIN) change request, an address changerequest, and/or the like. The second-level user account options may havea higher security requirement than the first-level user account options.

FIG. 5 is a flow chart of a method providing peer-to-peer paymentsaccording to an example embodiment. Referring to FIG. 5, the methodincludes: receiving, by the application 122, a first application usercredential at 502 from a user; and comparing, for a match, the firstapplication user credential with a stored second application usercredential at 504. These features may be substantially similar to thecorresponding features described above with reference to FIG. 4.

In response to receiving a request for a peer-to-peer payment (e.g., anin-person exchange of funds), the method may further include:communicating with a first contactless card 110 a using near fieldcommunication at 506; receiving, from the contactless card 110 a, apublic key of a key pair and card information at 508; instructing thecontactless card 110 a to generate a digital signature at 510; receivingthe digital signature from the contactless card 110 a at 512; verifyingthe digital signature at 514; and comparing, for a second match, atleast a portion of the user identity with at least a portion of thecardholder identification information at 516. These features may besubstantially similar to the corresponding features described above withreference to FIG. 4.

Once the first contactless card 110 a is verified, a prompt may bedisplayed requesting communication with the second contactless card 110b (e.g., a card tap). At 518, the application 122 communicates with thesecond contactless card 110 b using near field communication.Communication may involve receiving data from the second contactlesscard 110 b. For example, computing device 120 may receive a digitalsignature, a public key and/or card information from the secondcontactless card 110 b similar to that discussed with reference to thefirst contactless card 110 a. At 520, the processor 124 may transmitdata associated with the second contactless card 110 b and a request forpayment authorization to the account server 150. The account serverprocesses the request for payment and/or receipt either approves ordeclines the payment. At 522, the computing device 120 receives, fromthe account server 150, a status indicator of the request for paymentauthorization. The status request indicator may be an approved statusindicator or a declined status indicator. At 524, the application 122displays a visual representation of the status indicator on thecomputing device 120.

FIG. 6 is a flow chart of a method for communicating with a contactlesscard according to an example embodiment. The method 600 may be executed,for example, by computing device 120, for example, implementing a cardreader 126 (e.g., a reader application and a short-range antenna). At602, the application communicates with the contactless card 110 athrough near field communications. At 604, the communications mayinvolve the application 122 receiving, from the contactless card 110 a,card information including one or more of an activation field, the cardissuer identifier, and card-holder identification information. In somecases, application 122 may request specific data from contactless card110 a. The activation field indicates whether the contactless card 110 ais active (e.g., whether the card is activated or inactivated). The cardissuer identifier may represent an institution issuing or managing thecontactless card 110 a.

In response to receiving data indicating that contactless card 110 a isactivated (605-Yes), the application 122: receives, from the contactlesscard 110 a, a public key of a key pair at 606; instructs generation of adigital signature by the contactless card 110 a using a private key ofthe key pair of the card at 608; receives the digital signature from thecontactless card 110 a at 610; and verifies the digital signature usingthe public key at 612. The features described with reference to 606-612may be substantially similar to the relevant functions described abovewith reference to 508-514 of FIG. 5.

In response to verification of the digital signature, at 614, theapplication 122 grants the user access to first-level user accountoptions. At 616, in response to a user request for a second-level useraccount options (e.g., an attempt to transfer account assets), theapplication 122 may prompt the user for a first user credential (e.g.,biometrics data such as fingerprint data, optical data, and/or facialrecognition, an established gesture associated with the user, and/or ausername and password combination). The processor 124 compares at leasta portion of the first user credential and a stored second usercredential at 618. The stored user credential may be located on thecomputing device 120 and/or on the web server 140. At 620, in responseto finding a match, the application 122 grants the user access to thesecond-level user account options.

In response to determining the contactless card 110 a is inactivated(605-No), computing device 120 may activate the contactless card 110 a.For example, at 622, the computing device 120 transmits, to accountserver 150, at least a portion of the card information and a request toactivate the contactless card 110 a. The account server 150 processesthe request to activate the card by either approving or denyingactivation of the card. Responsive to transmitting the activationrequest, at 624, the computing device 120 receives a status indicator ofthe request to activate the contactless card 110 a from the accountserver 150. The status indicator may include an activated statusindicator or a denied status indicator. At 626, the application 122 maydisplay a visual representation of the status indicator. In someembodiments and as shown at 628, after the computing device 120 receivesan activated status indicator, the application 122 may instruct thecontactless card 110 a to update the activation field to reflect thecard as being activated.

In some embodiments, the contactless card 110 a may send a predetermineddigital signature and public key to the computing device 120 as the cardinformation. The computing device 120 may transmit, to the accountserver 150, and request verifification of the predetermined digitalsignature. In some cases, computing device 120 may further transmitadditional information (e.g., a network identifier, a device phonenumber or identification, other device information, etc.), which may beused as a validation check for activation, fraud prevention, highersecurity, and/or the like.

In some embodiments, a dedicated application 122 executing on computingdevice 120 may perform the activation of the contactless card 110 a. Inother embodiments, a webportal, a web-based app, an applet, and/or thelike may perform the activation. Activation may be performed on thecomputing device 120, or the computing device may merely act as a gobetween for the contactless card 110 a and an external device (e.g.,acount server 150). According to some embodiments, in providingactivation, the application 122 may indicate, to the account server 150,the type of device performing the activation (e.g., personal computer,smartphone, POS, or tablet). Further, the application 122 may output,for transmission, different and/or additional data to the account server150 depending on the type of device involved.

According to some embodiments, prior to performing card activation theapplication 122 requires the user to enter the first user credential fora user profile. The processor 124 verifies the first user credentialagainst a stored second user credential associated with the userprofile. The stored second user credential may be located on thecomputing device 120 and/or stored on a web server 140. In response tothe user logging onto the application 122, the application 122 maydisplay a plurality of user options (e.g., display of account balance,display of recent transactions, a card-activation option). Responsive toa user selection of the card-activation option from amongst theplurality of user options, the application 122 may output for display arequest to communicate with the contactless card 110 a.

In some embodiments, the example authentication communication protocolmay mimic an offline dynamic data authentication protocol of the EMVstandard that is commonly performed between a transaction card and apoint-of-sale device, with some modifications. For example, in thedisclosed embodiments, because the example authentication protocol isnot used to complete a payment transaction with a card issuer/paymentprocessor per se, some data values are not needed, and authenticationmay be performed without involving real-time online connectivity to thecard issuer/payment processor. As is known in the art, point of sale(POS) systems submit transactions including a transaction value to acard issuer. Whether the issuer approves or denies the transaction maybe based on if the card issuer recognizes the transaction value.Meanwhile, in certain embodiments of the present disclosure,transactions originating from a mobile device lack the transaction valueassociated with the POS systems. Therefore, in some embodiments, a dummytransaction value (i.e., a value recognizable to the card issuer andsufficient to allow activation to occur) may be passed as part of theexample authentication communication protocol. POS based transactionsmay also decline transactions based on the number of transactionattempts (e.g., transaction counter). A number of attempts beyond abuffer value may result in a soft decline; the soft decline requiringfurther verification before accepting the transaction. In someimplementations, a buffer value for the transaction counter may bemodified to avoid declining legitimate transactions.

Turning back to FIG. 6, in some cases, after activating the card, themethod may transition to 606 and/or 616. Moreover, as would beunderstood by one of ordinary skill, the blocks may be performed invarious orders, additional functions may be incorporated therebetween,and not all described functions may be performed in every embodiment.

FIG. 7 is a flow chart of a method for pairing a card to a deviceaccording to an example embodiment. According to some embodiments, anapplication 122 is enabled on a computing device 120. At 702,communication between the contactless card 110 a and the application 122begins when the contactless card is within an acceptable distance (e.g.,less than twenty centimeters) of the card reader 126 associated with theapplication 122. For example, application 122 may establish acommunication link with the contactless card 110 a using an NFCstandard. The computing device 120 receives, from the contactless card110 a, data associated with the card at 704. The data associated withthe card may include an unextracted public key of a public/private cardkey pair of the card. The unextracted public key may be previouslyencrypted by an issuer of contactless card 110 a using a private key ofa public/private issuer key pair. The application 122 using the issuerpublic key may extract the card public key.

In some embodiments, based on the data received from the contactlesscard 110 a, the computing device may verify the compatibility of thecontactless card 110 a with the application 122. For example, thecomputing device 120 may ensure only credit cards are paired with theapplication 122 as opposed to other devices using NFC (e.g., accesscards, tracking scanners). In some embodiments, the data received fromthe contactless card 110 a may be used to generate a virtual paymentcard as part of a digital wallet associated with the computing device120.

At 706, the computing device 120 transmits data to the contactless card110 a. The data may include instructions to generate a digital signatureusing the private key of the key pair. Responsive to generation of thedigital signature, the computing device 120 may receive the digitalsignature from the contactless card 110 a. The contactless card 110 amay be verified based on the digital signature and the public key of thepublic/private card key pair computing device 120. As detailed above,the use of this READ and WRITE NFC capability to perform offline dynamicdata authentication between a contactless card and a user's computingdevice provide unique advantages that enable application 122 to morereliably (e.g., with greater security from counterfeiting or cardskimming, or man in the middle attacks) authenticate the contactlesscard to be used as a form of multifactor authentication.

FIG. 9 is a flow chart of a method for activating a contactless cardaccording to an example embodiment. According to some embodiments, anapplication 122 is enabled on a computing device 120. The application122 communicates with the contactless card 110 a using, for example, NFCat 902. At 904, the computing device 120 receives data from thecontactless card 110 a, which may include activation field data, a cardissuer identifier, cardholder identification information, and/or thelike. At 906, the processor 124 transmits, to an account server 150, atleast a portion of the card-holder identification information and arequest to activate the contactless card 110 a. In some embodiments,based on the card issuer identifier, the processor 124 may determine aparticular account server of a plurality of account servers to transmitdata to. The processor 124 may receive a status indicator of the requestto activate the card at 908. The status indicator may be an activatedstatus indicator or a denied status indicator. At 910, the application122 displays a visual representation of the status indicator. In someembodiments and as shown at 912, the application 122 may instruct thecontactless card 110 a to update the activation field.

FIG. 10 is a timing diagram providing authenticated cardholder accessaccording to an example embodiment. Referring to FIG. 10, the methodincludes: receiving, by the application 122, a first application usercredential at 1002 from a user; communicating, by the application 122and to the processor 124, the first application user credential at 1004;comparing (e.g., for a match), the first application user credentialwith a stored second application user credential at 1006; communicatingthe comparison result from the processor 124 to the application 122, at1008; initiating, by the application 122, verification of the useridentity at 1010; and communicating with the contactless card 110 a at1012. These features may be substantially similar to the correspondingfeatures described above with reference to FIG. 2.

At 1014, in response to and the communication, the application 122receives, from the contactless card 110 a, an issuer public key of a keypair. The application 122 communicates the issuer public key to theprocessor 124 at 1016. Using the issuer public key, the processor 124verifies the card issuer at 1018, (e.g., by decrypting certain staticdata certified by the card issuer using the issuer public key). Inresponse to verifying the card issuer, at 1020, the processor 124communicates the verification result to the application 122.

At 1022, the contactless card 110 a sends the card public key of a cardpublic/private key pair and cardholder identification information to theapplication 122. In some embodiments, the cardholder identificationinformation and the card public key may be transmitted separately. At1024, the application 122 communicates the card public key to theprocessor 124. At 1026, using the card public key, the processor 124validates the card. The processor 124 communicates the validation resultto the application 122, at 1028.

At 1030, the application 122 instructs the contactless card 110 a togenerate a digital signature using the card private key of the cardpublic/private key pair. In response to generating the digitalsignature, the contactless card 110 a sends the digital signature to theapplication 122, at 1032. At 1034, the application 122 communicates thedigital signature to the processor 124. At 1036, the processor 124verifies the digital signature. The processor 124 may use the cardpublic key to verify the signature. Again, here, as detailed above, theimplementation of the above READ and WRITE NFC capability to performoffline dynamic data authentication between a contactless card and auser's computing device (and/or application executing on the device)provide unique advantages that enable application 122 to more reliably(e.g., with greater security from counterfeiting or card skimming, orman in the middle attacks) authenticate the contactless card to be usedas a form of multifactor authentication. At 1038, the processor 124compares, for a second match, at least a portion of the user identitywith at least a portion of the cardholder identification information.Subject to the second match, the user may be able to access second-leveluser account options.

FIG. 8 is a block diagram of an example computer system 800 that mayimplement certain aspects of the present disclosure. The computer system800 may include a set of instructions 826 for controlling operation ofthe computer system 800. In some implementations, the computer system800 may be connected (e.g., networked) to other machines in a Local AreaNetwork (LAN), an intranet, an extranet, a satellite communicationssystem, or the Internet. The computer system 800 may operate in thecapacity of a server or a client machine in a client-server networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The computer system 800 may be a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a server, a networkrouter, switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while a single computer system 800 isillustrated, the term “machine” shall also be taken to include anycollection of machines (e.g., computers) that individually or jointlyexecute a set (or multiple sets) of instructions to perform any one ormore of the methodologies discussed herein.

The computer system 800 includes a processing device 802, a main memory804 (e.g., read-only memory (ROM), flash memory, dynamic random-accessmemory (DRAM) such as synchronous DRAM (SDRAM), etc.), a static memory806 (e.g., flash memory, static random-access memory (SRAM), etc.), anda secondary memory 816 (e.g., a data storage device), which communicatewith each other via a bus 808.

The processing device 802 represents one or more general-purposeprocessing devices such as a microprocessor, a microcontroller, acentral processing unit, or the like. As non-limiting examples, theprocessing device 802 may be a reduced instruction set computing (RISC)microcontroller, a complex instruction set computing (CISC)microprocessor, a RISC microprocessor, very long instruction word (VLIW)microprocessor, a processor implementing other instruction sets, or oneor more processors implementing a combination of instruction sets. Theprocessing device 802 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like. The processing device 802 is configuredto execute the operations for electronically creating and tradingderivative products based on one or more indices relating to volatility.

The computer system 800 may further include a network interface device822, which is connectable to a network 130. The computer system 800 alsomay include a video display unit 810, i.e., a display (e.g., a liquidcrystal display (LCD), a touch screen, or a cathode ray tube (CRT)), analphanumeric input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), and a signal generation device 820 (e.g., aspeaker).

The secondary memory 816 may include a non-transitory storage medium 824on which is stored one or more sets of instructions 826 for the computersystem 800 representing any one or more of the methodologies orfunctions described herein. For example, the instructions 826 mayinclude instructions for implementing an asset tracking device includinga power source and power management system or subsystem for a containeror a trailer. The instructions 826 for the computer system 800 may alsoreside, completely or at least partially, within the main memory 804and/or within the processing device 802 during execution thereof by thecomputer system 800, the main memory 804 and the processing device 802also constituting computer-readable storage media.

While the storage medium 824 is shown in an example to be a singlemedium, the term “storage medium” should be taken to include a singlemedium or multiple media that store the one or more sets of instructionsfor a processing device. The term “storage medium” shall also be takento include any medium that is capable of storing or encoding a set ofinstructions for execution by the machine that cause the machine toperform any one or more of the methodologies of the disclosure. The term“storage medium” shall accordingly be taken to include, but not belimited to, solid-state memories, and optical and magnetic media.

Throughout the specification and the claims, the following terms take atleast the meanings explicitly associated herein, unless the contextclearly dictates otherwise. The term “or” is intended to mean aninclusive “or.” Further, the terms “a,” “an,” and “the” are intended tomean one or more unless specified otherwise or clear from the context tobe directed to a singular form.

In this description, numerous specific details have been set forth. Itis to be understood, however, that implementations of the disclosedtechnology may be practiced without these specific details. In otherinstances, well-known methods, structures and techniques have not beenshown in detail in order not to obscure an understanding of thisdescription. References to “one embodiment,” “an embodiment,” “someembodiments,” “example embodiment,” “various embodiments,” “oneimplementation,” “an implementation,” “example implementation,” “variousimplementations,” “some implementations,” etc., indicate that theimplementation(s) of the disclosed technology so described may include aparticular feature, structure, or characteristic, but not everyimplementation necessarily includes the particular feature, structure,or characteristic. Further, repeated use of the phrase “in oneimplementation” does not necessarily refer to the same implementation,although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

While certain implementations of the disclosed technology have beendescribed in connection with what is presently considered to be the mostpractical and various implementations, it is to be understood that thedisclosed technology is not to be limited to the disclosedimplementations, but on the contrary, is intended to cover variousmodifications and equivalent arrangements included within the scope ofthe appended claims. Although specific terms are employed herein, theyare used in a generic and descriptive sense only and not for purposes oflimitation.

This written description uses examples to disclose certainimplementations of the disclosed technology, including the best mode,and also to enable any person skilled in the art to practice certainimplementations of the disclosed technology, including making and usingany devices or systems and performing any incorporated methods. Thepatentable scope of certain implementations of the disclosed technologyis defined in the claims, and may include other examples that occur tothose skilled in the art. Such other examples are intended to be withinthe scope of the claims if they have structural elements that do notdiffer from the literal language of the claims, or if they includeequivalent structural elements with insubstantial differences from theliteral language of the claims.

Example Use Cases

The following example use cases describe examples of particularimplementations of the present disclosure. These are intended solely forexplanatory purposes and not for purposes of limitation. In one case, afirst friend (payor) owes a second friend (payee) a sum of money. Ratherthan going to an ATM or requiring exchange through a peer-to-peerapplication, payor wishes to pay via payee's smartphone (e.g., computingdevice 120). Payee logs-on to the appropriate application on hissmartphone and selects a payment request option. In response, theapplication requests authentication via payee's credit card. Forexample, the application outputs a display requesting that payee tap hisRFID credit card. Once payee taps his RFID credit card against thescreen of his smartphone with the application enabled, the card is readand verified. Next, the application displays a prompt for payor to taphis RFID card to send payment. After the payor taps his RFID card, theapplication reads the card information and transmits, via an associatedprocessor, a request for payment to payor's card issuer. The card issuerprocesses the transaction and sends a status indicator of thetransaction to the smartphone. The application then outputs for displaythe status indicator of the transaction.

In another example case, a credit card customer receives a new creditcard in the mail. Rather than activating the card by calling a providedtelephone number associated with the card issuer or visiting logginginto a website, the customer decides to activate the card via anapplication (e.g., application 122) on his smartphone (e.g., computingdevice 120). The customer selects the card activation feature from theapplication's menu. The application prompts the customer to tap his RFIDcredit card against the screen. Upon tapping the RFID credit cardagainst the screen of the smartphone, the application communicates witha card issuer server and activates the customer's card. The applicationthen displays a message indicating successful activation. The cardactivation is now complete.

In another example case, a customer wants to access his financialaccounts on his mobile phone. The customer launches an application (e.g,a bank application) on the mobile device and inputs a username andpassword. At this stage, the customer may see first-level accountinformation (e.g., recent purchases) and be able to perform first-levelaccount options (e.g., pay credit-card). However, if the user attemptsto access second-level account information (e.g., spending limit) orperform a second-level account option (e.g., transfer to externalsystem) he must have a second-factor authentication. Accordingly, theapplication requests that a user provide a transaction card (e.g.,credit card) for account verification. The user then taps his creditcard to the mobile device, and the application verifies that the creditcard corresponds to the user's account. Thereafter, the user may viewsecond-level account data and/or perform second-level account functions.

What is claimed is:
 1. A method for multi-level user authentication, themethod comprising: receiving, by an application associated with acomputing device, a first user credential from a user, the first usercredential associated with a user of an account having an associatedtransaction card provided by an account provider; determining that thefirst user credential matches a stored user credential, the stored usercredential associated with a user identity of the account; verifying theuser identity by: receiving, at the application, a public key of a keypair associated with the transaction card; instructing, by theapplication and via an antenna of the computing device configured tocommunicate with a radio frequency identification (RFID) chip in thetransaction card using near field communication (NFC), the transactioncard to generate a digital signature by using a private key of the keypair; receiving, at the application and via the antenna, the digitalsignature; and verifying, by the application, the digital signatureusing the public key; and determining, by the application, toauthenticate the user based on the verification of the digital signatureand the first user credential matching the stored user credential. 2.The method of claim 1, wherein the computing device is a mobile deviceassociated with the user.
 3. The method of claim 1, wherein the publickey is received from the transaction card, and wherein receiving thepublic key further comprises: receiving, via the antenna, a keycertificate associated with the public key.
 4. The method of claim 1,wherein the first user credential comprises at least one of biometricsdata, an established gesture associated with user recognition, or ausername and password combination.
 5. The method of claim 1, wherein theuser identity comprises at least one of a personal identification number(PIN), a name of the user, an address, or a date of birth.
 6. The methodof claim 1, further comprising: responsive to determining toauthenticate the user, performing the following: sending, with theapplication, cardholder data and a card activation request to an accountprovider server; receiving, at the application, a status of the cardactivation request, the status including activated or denied; anddisplaying, by the application, the status of the card activationrequest.
 7. The method of claim 1 further comprising: responsive todetermining that the first user credential matches the stored usercredential, providing, through the application, access to one or morefirst-level user account options of a user account; and responsive toverifying the digital signature, providing, through the application,access to one or more second-level user account options of the useraccount.
 8. The method of claim 7, wherein the user account is afinancial account, and the one or more first-level user account optionscomprises at least one of a display of an account balance or display ofrecent transactions.
 9. The method of claim 7, wherein the user accountis a financial account, and the one or more second-level user accountoptions comprises at least one of a payment transfer, a payment request,a personal identification number (PIN) change request, a card activationrequest, or an address change request.
 10. The method of claim 9,further comprising: receiving, by the application, the card activationrequest from the user; sending, by the application, cardholder data andthe card activation request to an account provider server; andreceiving, by the application, a status of the card activation request,the status including activated or denied.
 11. The method of claim 10,further comprising: displaying, by the application, the status of thecard activation request.
 12. A method for multi-level userauthentication, the method comprising: logging a user onto anapplication associated with a computing device by: receiving, at theapplication, a first user credential associated with a user profile ofthe user, the first user credential comprising at least one of:biometric data, a gesture, or a username and password combination; anddetermining, with the application, that the first user credentialmatches a stored user credential; displaying, on the application, aplurality of user account options; receiving, at the application, a userselection of a first-level user account option; providing, via theapplication, access to the first-level user account option; receiving,by the application, a user selection of a second-level user accountoption; displaying a request to verify the identity of the user inresponse to the selection of the second-level user account option;verifying the identity of the user by: receiving, by the application,card information from a card; and verifying, with the application, thatan account-holder of the card is associated with the user profile basedon the card information; and providing, by the application, access tothe second-level user account option.
 13. The method of claim 12,further comprising: sending, with the application, the card informationand a card activation request to an account provider server; receiving,at the application, a status of the card activation request, the statusincluding activated or denied; and displaying, by the application, thestatus of the card activation request.
 14. The method of claim 12,wherein receiving card information further comprises: communicating,using an antenna associated with the computing device, with a radiofrequency identification (RFID) chip in the card using near fieldcommunication (NFC).
 15. The method of claim 12, wherein: the method isperformed on a user device, the card is a virtual payment card, andreceiving card information comprises: accessing, with the application, adigital wallet on the user device, the digital wallet comprising thevirtual payment card; and retrieving, with the application, dataassociated with the virtual payment card.
 16. The method of claim 12,wherein receiving card information from the card further comprises:receiving, at the application, a key pair for the card; extracting, bythe application, an issuer public key from a public key certificateusing a certified public key; extracting, by the application, a publickey of the key pair for the card using the issuer public key;instructing, with the application, the card to generate a digitalsignature using a private key of the key pair; and verifying, with theapplication, the digital signature using the public key.
 17. The methodof claim 12, wherein the second-level user account option comprises atleast one of a payment transfer, a payment request, a personalidentification number (PIN) change request, a card activation request,or an address change request.
 18. A system for multi-level userauthentication, the system comprising: a computing device including anapplication and an antenna configured to communicate with a radiofrequency identification (RFID) chip in a transaction card using nearfield communication (NFC); one or more processors operable to run theapplication; and a memory in communication with the one or moreprocessors and storing instructions that, when executed by the one ormore processors, are configured to cause the system to: log a user ontothe application by: receiving a first user credential associated with auser profile of the user, the first user credential comprising at leastone of: biometric data, a gesture, or a username and passwordcombination; and determining that the first user credential matches astored second user credential; display, on the application, a pluralityof user account options; receive, at the application, a user selectionof a first-level user account option; provide, via the application,access to the first-level user account option, wherein the first-leveluser account option includes at least of: a display of an accountbalance or a display of recent transactions; receive, by theapplication, a user selection of a second-level user account option;display a request to verify the identity of the user in response to theselection of the second-level user account option, wherein thesecond-level user account option includes at least of: a paymenttransfer, a payment request, a personal identification number (PIN)change request, a card activation request, or an address change request;verify the identity of the user by: receiving, by the application andvia the antenna, card information from the transaction card; andverifying, with the application, that an account-holder of thetransaction card is associated with the user profile based on the cardinformation; and provide, by the application, access to the second-leveluser account option.
 19. The system of claim 18, further comprising:sending, with the application, the card information and the cardactivation request to an account provider server; receiving, at theapplication, a status of the card activation request, the statusincluding activated or denied; and displaying, by the application, thestatus of the card activation request.
 20. The system of claim 18,wherein receiving card information from the transaction card furthercomprises: receiving, at the application, a key pair for the transactioncard; extracting, by the application, an issuer public key from a publickey certificate using a certified public key; extracting, by theapplication, the public key of the key pair for the transaction cardusing the issuer public key; instructing, with the application, thetransaction card to generate a digital signature using a private key ofthe key pair; and verifying, with the application, the digital signatureusing the public key.